Local area data network connectivity

ABSTRACT

Certain aspects of the present disclosure relate to methods and apparatus relating to local area data network connectivity. In certain aspects, a method for use by a network device includes determining a set of available local area data networks (LADNs) for a user equipment (UE) based on a subscription of the UE to a set of data network names (DNNs) corresponding to the set of available LADNs and sending the UE information indicative of the set of available LADNs and a location of availability corresponding to each of the LADNs of the set of available LADNs.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a divisional of U.S. patent application Ser. No.15/927,378 entitled “LOCAL AREA DATA NETWORK CONNECTIVITY”, which wasfiled on Mar. 21, 2018 and claims the benefit of and priority to U.S.Provisional Application Ser. No. 62/477,255 entitled “LOCAL AREA DATANETWORK CONNECTIVITY,” which was filed Mar. 27, 2017. The aforementionedapplications are herein incorporated by reference in their entirety asif fully set forth below in their entirety and for all applicablepurposes.

FIELD

The present disclosure relates generally to communication systems, andmore particularly, to methods and apparatus relating to local area datanetwork connectivity.

BACKGROUND

Wireless communication systems are widely deployed to provide varioustelecommunication services such as telephony, video, data, messaging,and broadcasts. Typical wireless communication systems may employmultiple-access technologies capable of supporting communication withmultiple users by sharing available system resources (e.g., bandwidth,transmit power). Examples of such multiple-access technologies includeLong Term Evolution (LTE) systems, code division multiple access (CDMA)systems, time division multiple access (TDMA) systems, frequencydivision multiple access (FDMA) systems, orthogonal frequency divisionmultiple access (OFDMA) systems, single-carrier frequency divisionmultiple access (SC-FDMA) systems, and time division synchronous codedivision multiple access (TD-SCDMA) systems.

In some examples, a wireless multiple-access communication system mayinclude a number of base stations, each simultaneously supportingcommunication for multiple communication devices, otherwise known asuser equipment (UEs). In LTE or LTE-A network, a set of one or more basestations may define an eNodeB (eNB). In other examples (e.g., in a nextgeneration or 5G network), a wireless multiple access communicationsystem may include a number of distributed units (DUs) (e.g., edge units(EUs), edge nodes (ENs), radio heads (RHs), smart radio heads (SRHs),transmission reception points (TRPs), etc.) in communication with anumber of central units (CUs) (e.g., central nodes (CNs), access nodecontrollers (ANCs), etc.), where a set of one or more distributed units,in communication with a central unit, may define an access node (e.g., anew radio base station (NR BS), a new radio node-B (NR NB), a networknode, 5G NB, eNB, etc.). A base station or DU may communicate with a setof UEs on downlink channels (e.g., for transmissions from a base stationor to a UE) and uplink channels (e.g., for transmissions from a UE to abase station or distributed unit).

These multiple access technologies have been adopted in varioustelecommunication standards to provide a common protocol that enablesdifferent wireless devices to communicate on a municipal, national,regional, and even global level. An example of an emergingtelecommunication standard is new radio (NR), for example, 5G radioaccess. NR is a set of enhancements to the LTE mobile standardpromulgated by Third Generation Partnership Project (3GPP). It isdesigned to better support mobile broadband Internet access by improvingspectral efficiency, lowering costs, improving services, making use ofnew spectrum, and better integrating with other open standards usingOFDMA with a cyclic prefix (CP) on the downlink (DL) and on the uplink(UL) as well as support beamforming, multiple-input multiple-output(MIMO) antenna technology, and carrier aggregation.

However, as the demand for mobile broadband access continues toincrease, there exists a desire for further improvements in NRtechnology. Preferably, these improvements should be applicable to othermulti-access technologies and the telecommunication standards thatemploy these technologies.

BRIEF SUMMARY

The systems, methods, and devices of the disclosure each have severalaspects, no single one of which is solely responsible for its desirableattributes. Without limiting the scope of this disclosure as expressedby the claims which follow, some features will now be discussed briefly.After considering this discussion, and particularly after reading thesection entitled “Detailed Description” one will understand how thefeatures of this disclosure provide advantages that include improvedcommunications between access points and stations in a wireless network.

Certain aspects provide a method for wireless communications by anaccess and mobility management function (AMF). The method generallyincludes determining a set of available local area data networks (LADNs)for a user equipment (UE) based on a subscription of the UE to a set ofdata network names (DNNs) corresponding to the set of available LADNsand sending the UE information indicative of the set of available LADNsand a location of availability corresponding to each of the LADNs of theset of available LADNs.

Certain aspects provide a method for wireless communications by userequipment (UE). The method generally includes requesting informationrelating to one or more local area data networks (LADNs) from an accessand mobility management function (AMF), receiving information from theAMF corresponding to a set of available LADNs and an area ofavailability corresponding to each of the LADNs of the set of availableLADNs, wherein the UE has a subscription to a set of data network names(DNNs) corresponding to the set of available LADNs, and establishing aprotocol data unit (PDU) session to one LADN of the set of availableLADNs based on the information received from the AMF.

Certain aspects provide a method for wireless communications by anaccess and mobility management function (AMF). The method generallyincludes determining that a user equipment (UE) has moved outside of anarea of availability corresponding to a local area data network (LADN)to which the UE has an established protocol data unit (PDU) session andsending a notification request to a session management function (SMF)serving the PDU session after the determining.

Certain aspects provide a method for wireless communications by an asession management function (SMF). The method generally includesreceiving a notification from an access and mobility management function(AMF) that a user equipment (UE) has moved outside of an area ofavailability corresponding to a local area data network (LADN) to whichthe UE has an established protocol data unit (PDU) session and making achange to the PDU session being served by the SMF in response to thenotification.

Certain aspects provide a method for wireless communications by an asession management function (SMF). The method generally includesreceiving a request from a session management function (SMF) serving aprotocol data unit (PDU) session that a UE has established with a localarea data network (LADN) to provide the SMF with information about alocation of the UE and providing the SMF with a notification includinginformation about the location of the UE.

Aspects generally include methods, apparatus, systems, computer readablemediums, and processing systems, as substantially described herein withreference to and as illustrated by the accompanying drawings.

To the accomplishment of the foregoing and related ends, the one or moreaspects comprise the features hereinafter fully described andparticularly pointed out in the claims. The following description andthe annexed drawings set forth in detail certain illustrative featuresof the one or more aspects. These features are indicative, however, ofbut a few of the various ways in which the principles of various aspectsmay be employed, and this description is intended to include all suchaspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the manner in which the above-recited features of the presentdisclosure can be understood in detail, a more particular description,briefly summarized above, may be had by reference to aspects, some ofwhich are illustrated in the appended drawings. It is to be noted,however, that the appended drawings illustrate only certain typicalaspects of this disclosure and are therefore not to be consideredlimiting of its scope, for the description may admit to other equallyeffective aspects.

FIG. 1 is a block diagram conceptually illustrating an exampletelecommunications system, in accordance with certain aspects of thepresent disclosure.

FIG. 2 is a block diagram illustrating an example logical architectureof a distributed RAN, in accordance with certain aspects of the presentdisclosure.

FIG. 3 is a diagram illustrating an example physical architecture of adistributed RAN, in accordance with certain aspects of the presentdisclosure.

FIG. 4 is a block diagram conceptually illustrating a design of anexample BS and user equipment (UE), in accordance with certain aspectsof the present disclosure.

FIG. 5 is a diagram showing examples for implementing a communicationprotocol stack, in accordance with certain aspects of the presentdisclosure.

FIG. 6 illustrates an example of a DL-centric subframe, in accordancewith certain aspects of the present disclosure.

FIG. 7 illustrates an example of an UL-centric subframe, in accordancewith certain aspects of the present disclosure.

FIG. 8 illustrates example non-roaming 5G system architecture, inaccordance with certain aspects of the present disclosure.

FIG. 9 illustrates example non-roaming 5G system architecture for UE(s)concurrently accessing two (e.g. local and central) data networks usingmultiple PDU sessions, in accordance with certain aspects of the presentdisclosure.

FIG. 10 illustrates example roaming 5G system architecture in caseswhere there is a local break out with AF in VPLMN, in accordance withcertain aspects of the present disclosure.

FIG. 11 illustrates example roaming 5G system architecture in a homerouted scenario using the reference point representation, in accordancewith certain aspects of the present disclosure.

FIG. 12 illustrates example connection management state models, inaccordance with certain aspects of the present disclosure.

FIG. 13 illustrates example operations for use by an access and mobilitymanagement function (AMF), in accordance with aspects of the presentdisclosure.

FIG. 13A illustrates a communications device that may include variouscomponents configured to perform the operations of FIG. 13, inaccordance with aspects of the present disclosure.

FIG. 14 illustrates example operations for use by a UE, in accordancewith aspects of the present disclosure.

FIG. 14A illustrates a communications device that may include variouscomponents configured to perform the operations of FIG. 14, inaccordance with aspects of the present disclosure.

FIG. 15 illustrates example operations for use by an AMF, in accordancewith aspects of the present disclosure.

FIG. 15A illustrates a communications device that may include variouscomponents configured to perform the operations of FIG. 15, inaccordance with aspects of the present disclosure.

FIG. 16 illustrates example operations for use by an SMF, in accordancewith aspects of the present disclosure.

FIG. 16A illustrates a communications device that may include variouscomponents configured to perform the operations of FIG. 16, inaccordance with aspects of the present disclosure.

FIG. 17 illustrates example operations for use by an AMF, in accordancewith aspects of the present disclosure.

FIG. 17A illustrates a communications device that may include variouscomponents configured to perform the operations of FIG. 17, inaccordance with aspects of the present disclosure.

To facilitate understanding, identical reference numerals have beenused, where possible, to designate identical elements that are common tothe figures. It is contemplated that elements disclosed in one aspectmay be beneficially utilized on other aspects without specificrecitation.

DETAILED DESCRIPTION

Aspects of the present disclosure relate to methods and apparatusrelating to local area data network connectivity.

Aspects of the present disclosure provide apparatus, methods, processingsystems, and computer readable mediums for new radio (NR) (new radioaccess technology or 5G technology).

NR may support various wireless communication services, such as Enhancedmobile broadband (eMBB) targeting wide bandwidth (e.g. 80 MHz beyond),millimeter wave (mmW) targeting high carrier frequency (e.g. 60 GHz),massive MTC (mMTC) targeting non-backward compatible MTC techniques,and/or mission critical targeting ultra-reliable low latencycommunications (URLLC). These services may include latency andreliability requirements. These services may also have differenttransmission time intervals (TTI) to meet respective quality of service(QoS) requirements. In addition, these services may co-exist in the samesubframe.

5G or NR Systems may provide support for the UEs (e.g., UE 120) toconnect to a local area data network (LADN) reachable within a certainarea. In order to enable the UE 120 to connect to the LADN, the 5Gsystem may send a notification to the UE including information about theLADN and its availability, etc. In some embodiments, based on the LADNinformation received in the notification, the UE 120 may then establisha PDU session to the LADN while the UE 120 is located in the area.Certain embodiments described herein relate to details of whatinformation (e.g. granularity of location) is provided to the UE 120,when it is provided, and how it is provided. In addition, certainembodiments described herein relate to how an LADN PDU session istreated or managed as the UE 120 moves in and out of the LADN's area ofavailability. As an example, when the UE 120 moves outside the LADN'sarea of availability, the PDU session may be suspended or released.

The following description provides examples, and is not limiting of thescope, applicability, or examples set forth in the claims. Changes maybe made in the function and arrangement of elements discussed withoutdeparting from the scope of the disclosure. Various examples may omit,substitute, or add various procedures or components as appropriate. Forinstance, the methods described may be performed in an order differentfrom that described, and various steps may be added, omitted, orcombined. Also, features described with respect to some examples may becombined in some other examples. For example, an apparatus may beimplemented or a method may be practiced using any number of the aspectsset forth herein. In addition, the scope of the disclosure is intendedto cover such an apparatus or method which is practiced using otherstructure, functionality, or structure and functionality in addition toor other than the various aspects of the disclosure set forth herein. Itshould be understood that any aspect of the disclosure disclosed hereinmay be embodied by one or more elements of a claim. The word “exemplary”is used herein to mean “serving as an example, instance, orillustration.” Any aspect described herein as “exemplary” is notnecessarily to be construed as preferred or advantageous over otheraspects.

The techniques described herein may be used for various wirelesscommunication networks such as LTE, CDMA, TDMA, FDMA, OFDMA, SC-FDMA andother networks. The terms “network” and “system” are often usedinterchangeably. A CDMA network may implement a radio technology such asUniversal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includesWideband CDMA (WCDMA) and other variants of CDMA. cdma2000 coversIS-2000, IS-95 and IS-856 standards. A TDMA network may implement aradio technology such as Global System for Mobile Communications (GSM).An OFDMA network may implement a radio technology such as NR (e.g. 5GRA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11(Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA andE-UTRA are part of Universal Mobile Telecommunication System (UMTS). NRis an emerging wireless communications technology under development inconjunction with the 5G Technology Forum (5GTF). 3GPP Long TermEvolution (LTE) and LTE-Advanced (LTE-A) are releases of UMTS that useE-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described indocuments from an organization named “3rd Generation PartnershipProject” (3GPP). cdma2000 and UMB are described in documents from anorganization named “3rd Generation Partnership Project 2” (3GPP2). Thetechniques described herein may be used for the wireless networks andradio technologies mentioned above as well as other wireless networksand radio technologies. For clarity, while aspects may be describedherein using terminology commonly associated with 3G and/or 4G wirelesstechnologies, aspects of the present disclosure can be applied in othergeneration-based communication systems, such as 5G and later, includingNR technologies.

Example Wireless Communications System

FIG. 1 illustrates an example wireless network 100, such as a new radio(NR) or 5G network, in which aspects of the present disclosure may beperformed.

As illustrated in FIG. 1, the wireless network 100 may include a numberof BSs 110 and other network entities. A BS may be a station thatcommunicates with UEs. Each BS 110 may provide communication coveragefor a particular geographic area. In 3GPP, the term “cell” can refer toa coverage area of a Node B and/or a Node B subsystem serving thiscoverage area, depending on the context in which the term is used. In NRsystems, the term “cell” and eNB, Node B, 5G NB, AP, NR BS, NR BS, orTRP may be interchangeable. In some examples, a cell may not necessarilybe stationary, and the geographic area of the cell may move according tothe location of a mobile base station. In some examples, the basestations may be interconnected to one another and/or to one or moreother base stations or network nodes (not shown) in the wireless network100 through various types of backhaul interfaces such as a directphysical connection, a virtual network, or the like using any suitabletransport network.

In general, any number of wireless networks may be deployed in a givengeographic area. Each wireless network may support a particular radioaccess technology (RAT) and may operate on one or more frequencies. ARAT may also be referred to as a radio technology, an air interface,etc. A frequency may also be referred to as a carrier, a frequencychannel, etc. Each frequency may support a single RAT in a givengeographic area in order to avoid interference between wireless networksof different RATs. In some cases, NR or 5G RAT networks may be deployed.

A BS may provide communication coverage for a macro cell, a pico cell, afemto cell, and/or other types of cell. A macro cell may cover arelatively large geographic area (e.g., several kilometers in radius)and may allow unrestricted access by UEs with service subscription. Apico cell may cover a relatively small geographic area and may allowunrestricted access by UEs with service subscription. A femto cell maycover a relatively small geographic area (e.g., a home) and may allowrestricted access by UEs having association with the femto cell (e.g.,UEs in a Closed Subscriber Group (CSG), UEs for users in the home,etc.). ABS for a macro cell may be referred to as a macro BS. A BS for apico cell may be referred to as a pico BS. A BS for a femto cell may bereferred to as a femto BS or a home BS. In the example shown in FIG. 1,the BSs 110 a, 110 b and 110 c may be macro BSs for the macro cells 102a, 102 b and 102 c, respectively. The BS 110 x may be a pico BS for apico cell 102 x. The BSs 110 y and 110 z may be femto BS for the femtocells 102 y and 102 z, respectively. ABS may support one or multiple(e.g., three) cells.

The wireless network 100 may also include relay stations. A relaystation is a station that receives a transmission of data and/or otherinformation from an upstream station (e.g., a BS or a UE) and sends atransmission of the data and/or other information to a downstreamstation (e.g., a UE or a BS). A relay station may also be a UE thatrelays transmissions for other UEs. In the example shown in FIG. 1, arelay station 110 r may communicate with the BS 110 a and a UE 120 r inorder to facilitate communication between the BS 110 a and the UE 120 r.A relay station may also be referred to as a relay BS, a relay, etc.

The wireless network 100 may be a heterogeneous network that includesBSs of different types, e.g., macro BS, pico BS, femto BS, relays, etc.These different types of BSs may have different transmit power levels,different coverage areas, and different impact on interference in thewireless network 100. For example, macro BS may have a high transmitpower level (e.g., 20 Watts) whereas pico BS, femto BS, and relays mayhave a lower transmit power level (e.g., 1 Watt).

The wireless network 100 may support synchronous or asynchronousoperation. For synchronous operation, the BSs may have similar frametiming, and transmissions from different BSs may be approximatelyaligned in time. For asynchronous operation, the BSs may have differentframe timing, and transmissions from different BSs may not be aligned intime. The techniques described herein may be used for both synchronousand asynchronous operation.

A network controller 130 may be coupled to a set of BSs and providecoordination and control for these BSs. The network controller 130 maycommunicate with the BSs 110 via a backhaul. The BSs 110 may alsocommunicate with one another, e.g., directly or indirectly via wirelessor wireline backhaul.

The UEs 120 (e.g., 120 x, 120 y, etc.) may be dispersed throughout thewireless network 100, and each UE may be stationary or mobile. A UE mayalso be referred to as a mobile station, a terminal, an access terminal,a subscriber unit, a station, a Customer Premises Equipment (CPE), acellular phone, a smart phone, a personal digital assistant (PDA), awireless modem, a wireless communication device, a handheld device, alaptop computer, a cordless phone, a wireless local loop (WLL) station,a tablet, a camera, a gaming device, a netbook, a smartbook, anultrabook, a medical device or medical equipment, a biometricsensor/device, a wearable device such as a smart watch, smart clothing,smart glasses, a smart wrist band, smart jewelry (e.g., a smart ring, asmart bracelet, etc.), an entertainment device (e.g., a music device, avideo device, a satellite radio, etc.), a vehicular component or sensor,a smart meter/sensor, industrial manufacturing equipment, a globalpositioning system device, or any other suitable device that isconfigured to communicate via a wireless or wired medium. Some UEs maybe considered evolved or machine-type communication (MTC) devices orevolved MTC (eMTC) devices. MTC and eMTC UEs include, for example,robots, drones, remote devices, sensors, meters, monitors, locationtags, etc., that may communicate with a BS, another device (e.g., remotedevice), or some other entity. A wireless node may provide, for example,connectivity for or to a network (e.g., a wide area network such asInternet or a cellular network) via a wired or wireless communicationlink. Some UEs may be considered Internet-of-Things (IoT) devices. InFIG. 1, a solid line with double arrows indicates desired transmissionsbetween a UE and a serving BS, which is a BS designated to serve the UEon the downlink and/or uplink. A dashed line with double arrowsindicates interfering transmissions between a UE and a BS.

Certain wireless networks (e.g., LTE) utilize orthogonal frequencydivision multiplexing (OFDM) on the downlink and single-carrierfrequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDMpartition the system bandwidth into multiple (K) orthogonal subcarriers,which are also commonly referred to as tones, bins, etc. Each subcarriermay be modulated with data. In general, modulation symbols are sent inthe frequency domain with OFDM and in the time domain with SC-FDM. Thespacing between adjacent subcarriers may be fixed, and the total numberof subcarriers (K) may be dependent on the system bandwidth. Forexample, the spacing of the subcarriers may be 15 kHz and the minimumresource allocation (called a ‘resource block’) may be 12 subcarriers(or 180 kHz). Consequently, the nominal FFT size may be equal to 128,256, 512, 1024 or 2048 for system bandwidth of 1.25, 2.5, 5, 10 or 20megahertz (MHz), respectively. The system bandwidth may also bepartitioned into subbands. For example, a subband may cover 1.08 MHz(i.e., 6 resource blocks), and there may be 1, 2, 4, 8 or 16 subbandsfor system bandwidth of 1.25, 2.5, 5, 10 or 20 MHz, respectively.

While aspects of the examples described herein may be associated withLTE technologies, aspects of the present disclosure may be applicablewith other wireless communications systems, such as NR. NR may utilizeOFDM with a CP on the uplink and downlink and include support forhalf-duplex operation using time division duplex (TDD). A singlecomponent carrier bandwidth of 100 MHz may be supported. NR resourceblocks may span 12 sub-carriers with a sub-carrier bandwidth of 75 kHzover a 0.1 ms duration. Each radio frame may consist of 50 subframeswith a length of 10 ms. Consequently, each subframe may have a length of0.2 ms. Each subframe may indicate a link direction (i.e., DL or UL) fordata transmission and the link direction for each subframe may bedynamically switched. Each subframe may include DL/UL data as well asDL/UL control data. UL and DL subframes for NR may be as described inmore detail below with respect to FIGS. 6 and 7. Beamforming may besupported and beam direction may be dynamically configured. MIMOtransmissions with precoding may also be supported. MIMO configurationsin the DL may support up to 8 transmit antennas with multi-layer DLtransmissions up to 8 streams and up to 2 streams per UE. Multi-layertransmissions with up to 2 streams per UE may be supported. Aggregationof multiple cells may be supported with up to 8 serving cells.Alternatively, NR may support a different air interface, other than anOFDM-based. NR networks may include entities such CUs and/or DUs.

In some examples, access to the air interface may be scheduled, whereina scheduling entity (e.g., a base station) allocates resources forcommunication among some or all devices and equipment within its servicearea or cell. Within the present disclosure, as discussed further below,the scheduling entity may be responsible for scheduling, assigning,reconfiguring, and releasing resources for one or more subordinateentities. That is, for scheduled communication, subordinate entitiesutilize resources allocated by the scheduling entity. Base stations arenot the only entities that may function as a scheduling entity. That is,in some examples, a UE may function as a scheduling entity, schedulingresources for one or more subordinate entities (e.g., one or more otherUEs). In this example, the UE is functioning as a scheduling entity, andother UEs utilize resources scheduled by the UE for wirelesscommunication. A UE may function as a scheduling entity in apeer-to-peer (P2P) network, and/or in a mesh network. In a mesh networkexample, UEs may optionally communicate directly with one another inaddition to communicating with the scheduling entity.

Thus, in a wireless communication network with a scheduled access totime-frequency resources and having a cellular configuration, a P2Pconfiguration, and a mesh configuration, a scheduling entity and one ormore subordinate entities may communicate utilizing the scheduledresources.

As noted above, a RAN may include a CU and DUs. A NR BS (e.g., eNB, 5GNode B, Node B, transmission reception point (TRP), access point (AP))may correspond to one or multiple BSs. NR cells can be configured asaccess cell (ACells) or data only cells (DCells). For example, the RAN(e.g., a central unit or distributed unit) can configure the cells.DCells may be cells used for carrier aggregation or dual connectivity,but not used for initial access, cell selection/reselection, orhandover. In some cases DCells may not transmit synchronizationsignals—in some case cases DCells may transmit SS. NR BSs may transmitdownlink signals to UEs indicating the cell type. Based on the cell typeindication, the UE may communicate with the NR BS. For example, the UEmay determine NR BSs to consider for cell selection, access, handover,and/or measurement based on the indicated cell type.

FIG. 2 illustrates an example logical architecture of a distributedradio access network (RAN) 200, which may be implemented in the wirelesscommunication system illustrated in FIG. 1. A 5G access node 206 mayinclude an access node controller (ANC) 202. The ANC may be a centralunit (CU) of the distributed RAN 200. The backhaul interface to the nextgeneration core network (NG-CN) 204 may terminate at the ANC. Thebackhaul interface to neighboring next generation access nodes (NG-ANs)may terminate at the ANC. The ANC may include one or more TRPs 208(which may also be referred to as BSs, NR BSs, Node Bs, 5G NBs, APs, orsome other term). As described above, a TRP may be used interchangeablywith “cell.”

The TRPs 208 may be a DU. The TRPs may be connected to one ANC (ANC 202)or more than one ANC (not illustrated). For example, for RAN sharing,radio as a service (RaaS), and service specific AND deployments, the TRPmay be connected to more than one ANC. A TRP may include one or moreantenna ports. The TRPs may be configured to individually (e.g., dynamicselection) or jointly (e.g., joint transmission) serve traffic to a UE.

The local architecture 200 may be used to illustrate fronthauldefinition. The architecture may be defined that support fronthaulingsolutions across different deployment types. For example, thearchitecture may be based on transmit network capabilities (e.g.,bandwidth, latency, and/or jitter).

The architecture may share features and/or components with LTE.According to aspects, the next generation AN (NG-AN) 210 may supportdual connectivity with NR. The NG-AN may share a common fronthaul forLTE and NR.

The architecture may enable cooperation between and among TRPs 208. Forexample, cooperation may be preset within a TRP and/or across TRPs viathe ANC 202. According to aspects, no inter-TRP interface may beneeded/present.

According to aspects, a dynamic configuration of split logical functionsmay be present within the architecture 200. As will be described in moredetail with reference to FIG. 5, the Radio Resource Control (RRC) layer,Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC)layer, Medium Access Control (MAC) layer, and a Physical (PHY) layersmay be adaptably placed at the DU or CU (e.g., TRP or ANC,respectively). According to certain aspects, a BS may include a centralunit (CU) (e.g., ANC 202) and/or one or more distributed units (e.g.,one or more TRPs 208).

FIG. 3 illustrates an example physical architecture of a distributed RAN300, according to aspects of the present disclosure. A centralized corenetwork unit (C-CU) 302 may host core network functions. The C-CU may becentrally deployed. C-CU functionality may be offloaded (e.g., toadvanced wireless services (AWS)), in an effort to handle peak capacity.

A centralized RAN unit (C-RU) 304 may host one or more ANC functions.Optionally, the C-RU may host core network functions locally. The C-RUmay have distributed deployment. The C-RU may be closer to the networkedge.

A DU 306 may host one or more TRPs (edge node (EN), an edge unit (EU), aradio head (RH), a smart radio head (SRH), or the like). The DU may belocated at edges of the network with radio frequency (RF) functionality.

FIG. 4 illustrates example components of the BS 110 and UE 120illustrated in FIG. 1, which may be used to implement aspects of thepresent disclosure. As described above, the BS may include a TRP. One ormore components of the BS 110 and UE 120 may be used to practice aspectsof the present disclosure. For example, antennas 452, Tx/Rx 222,processors 466, 458, 464, and/or controller/processor 480 of the UE 120and/or antennas 434, processors 460, 420, 438, and/orcontroller/processor 440 of the BS 110 may be used to perform theoperations described herein and illustrated with reference to FIGS.13-16.

FIG. 4 shows a block diagram of a design of a BS 110 and a UE 120, whichmay be one of the BSs and one of the UEs in FIG. 1. For a restrictedassociation scenario, the base station 110 may be the macro BS 110 c inFIG. 1, and the UE 120 may be the UE 120 y. The base station 110 mayalso be a base station of some other type. The base station 110 may beequipped with antennas 434 a through 434 t, and the UE 120 may beequipped with antennas 452 a through 452 r.

At the base station 110, a transmit processor 420 may receive data froma data source 412 and control information from a controller/processor440. The control information may be for the Physical Broadcast Channel(PBCH), Physical Control Format Indicator Channel (PCFICH), PhysicalHybrid ARQ Indicator Channel (PHICH), Physical Downlink Control Channel(PDCCH), etc. The data may be for the Physical Downlink Shared Channel(PDSCH), etc. The processor 420 may process (e.g., encode and symbolmap) the data and control information to obtain data symbols and controlsymbols, respectively. The processor 420 may also generate referencesymbols, e.g., for the PSS, SSS, and cell-specific reference signal. Atransmit (TX) multiple-input multiple-output (MIMO) processor 430 mayperform spatial processing (e.g., precoding) on the data symbols, thecontrol symbols, and/or the reference symbols, if applicable, and mayprovide output symbol streams to the modulators (MODs) 432 a through 432t. For example, the TX MIMO processor 430 may perform certain aspectsdescribed herein for RS multiplexing. Each modulator 432 may process arespective output symbol stream (e.g., for OFDM, etc.) to obtain anoutput sample stream. Each modulator 432 may further process (e.g.,convert to analog, amplify, filter, and upconvert) the output samplestream to obtain a downlink signal. Downlink signals from modulators 432a through 432 t may be transmitted via the antennas 434 a through 434 t,respectively.

At the UE 120, the antennas 452 a through 452 r may receive the downlinksignals from the base station 110 and may provide received signals tothe demodulators (DEMODs) 454 a through 454 r, respectively. Eachdemodulator 454 may condition (e.g., filter, amplify, downconvert, anddigitize) a respective received signal to obtain input samples. Eachdemodulator 454 may further process the input samples (e.g., for OFDM,etc.) to obtain received symbols. A MIMO detector 456 may obtainreceived symbols from all the demodulators 454 a through 454 r, performMIMO detection on the received symbols if applicable, and providedetected symbols. For example, MIMO detector 456 may provide detected RStransmitted using techniques described herein. A receive processor 458may process (e.g., demodulate, deinterleave, and decode) the detectedsymbols, provide decoded data for the UE 120 to a data sink 460, andprovide decoded control information to a controller/processor 480.According to one or more cases, CoMP aspects can include providing theantennas, as well as some Tx/Rx functionalities, such that they residein distributed units. For example, some Tx/Rx processings can be done inthe central unit, while other processing can be done at the distributedunits. For example, in accordance with one or more aspects as shown inthe diagram, the BS mod/demod 432 may be in the distributed units.

On the uplink, at the UE 120, a transmit processor 464 may receive andprocess data (e.g., for the Physical Uplink Shared Channel (PUSCH)) froma data source 462 and control information (e.g., for the Physical UplinkControl Channel (PUCCH) from the controller/processor 480. The transmitprocessor 464 may also generate reference symbols for a referencesignal. The symbols from the transmit processor 464 may be precoded by aTX MIMO processor 466 if applicable, further processed by thedemodulators 454 a through 454 r (e.g., for SC-FDM, etc.), andtransmitted to the base station 110. At the BS 110, the uplink signalsfrom the UE 120 may be received by the antennas 434, processed by themodulators 432, detected by a MIMO detector 436 if applicable, andfurther processed by a receive processor 438 to obtain decoded data andcontrol information sent by the UE 120. The receive processor 438 mayprovide the decoded data to a data sink 439 and the decoded controlinformation to the controller/processor 440.

The controllers/processors 440 and 480 may direct the operation at thebase station 110 and the UE 120, respectively. The processor 440 and/orother processors and modules at the base station 110 may perform ordirect, e.g., the execution of the functional blocks illustrated inFIGS. 13-16, and/or other processes for the techniques described herein.The processor 480 and/or other processors and modules at the UE 120 mayalso perform or direct processes for the techniques described herein.The memories 442 and 482 may store data and program codes for the BS 110and the UE 120, respectively. A scheduler 444 may schedule UEs for datatransmission on the downlink and/or uplink.

FIG. 5 illustrates a diagram 500 showing examples for implementing acommunications protocol stack, according to aspects of the presentdisclosure. The illustrated communications protocol stacks may beimplemented by devices operating in a in a 5G system (e.g., a systemthat supports uplink-based mobility). Diagram 500 illustrates acommunications protocol stack including a Radio Resource Control (RRC)layer 510, a Packet Data Convergence Protocol (PDCP) layer 515, a RadioLink Control (RLC) layer 520, a Medium Access Control (MAC) layer 525,and a Physical (PHY) layer 530. In various examples the layers of aprotocol stack may be implemented as separate modules of software,portions of a processor or ASIC, portions of non-collocated devicesconnected by a communications link, or various combinations thereof.Collocated and non-collocated implementations may be used, for example,in a protocol stack for a network access device (e.g., ANs, CUs, and/orDUs) or a UE.

A first option 505-a shows a split implementation of a protocol stack,in which implementation of the protocol stack is split between acentralized network access device (e.g., an ANC 202 in FIG. 2) anddistributed network access device (e.g., DU 208 in FIG. 2). In the firstoption 505-a, an RRC layer 510 and a PDCP layer 515 may be implementedby the central unit, and an RLC layer 520, a MAC layer 525, and a PHYlayer 530 may be implemented by the DU. In various examples the CU andthe DU may be collocated or non-collocated. The first option 505-a maybe useful in a macro cell, micro cell, or pico cell deployment.

A second option 505-b shows a unified implementation of a protocolstack, in which the protocol stack is implemented in a single networkaccess device (e.g., access node (AN), new radio base station (NR BS), anew radio Node-B (NR NB), a network node (NN), or the like.). In thesecond option, the RRC layer 510, the PDCP layer 515, the RLC layer 520,the MAC layer 525, and the PHY layer 530 may each be implemented by theAN. The second option 505-b may be useful in a femto cell deployment.

Regardless of whether a network access device implements part or all ofa protocol stack, a UE may implement an entire protocol stack (e.g., theRRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525,and the PHY layer 530).

FIG. 6 is a diagram 600 showing an example of a DL-centric subframe. TheDL-centric subframe may include a control portion 602. The controlportion 602 may exist in the initial or beginning portion of theDL-centric subframe. The control portion 602 may include variousscheduling information and/or control information corresponding tovarious portions of the DL-centric subframe. In some configurations, thecontrol portion 602 may be a physical DL control channel (PDCCH), asindicated in FIG. 6. The DL-centric subframe may also include a DL dataportion 604. The DL data portion 604 may sometimes be referred to as thepayload of the DL-centric subframe. The DL data portion 604 may includethe communication resources utilized to communicate DL data from thescheduling entity (e.g., UE or BS) to the subordinate entity (e.g., UE).In some configurations, the DL data portion 604 may be a physical DLshared channel (PDSCH).

The DL-centric subframe may also include a common UL portion 606. Thecommon UL portion 606 may sometimes be referred to as an UL burst, acommon UL burst, and/or various other suitable terms. The common ULportion 606 may include feedback information corresponding to variousother portions of the DL-centric subframe. For example, the common ULportion 606 may include feedback information corresponding to thecontrol portion 602. Non-limiting examples of feedback information mayinclude an ACK signal, a NACK signal, a HARQ indicator, and/or variousother suitable types of information. The common UL portion 606 mayinclude additional or alternative information, such as informationpertaining to random access channel (RACH) procedures, schedulingrequests (SRs), and various other suitable types of information. Asillustrated in FIG. 6, the end of the DL data portion 604 may beseparated in time from the beginning of the common UL portion 606. Thistime separation may sometimes be referred to as a gap, a guard period, aguard interval, and/or various other suitable terms. This separationprovides time for the switch-over from DL communication (e.g., receptionoperation by the subordinate entity (e.g., UE)) to UL communication(e.g., transmission by the subordinate entity (e.g., UE)). One ofordinary skill in the art will understand that the foregoing is merelyone example of a DL-centric subframe and alternative structures havingsimilar features may exist without necessarily deviating from theaspects described herein.

FIG. 7 is a diagram 700 showing an example of an UL-centric subframe.The UL-centric subframe may include a control portion 702. The controlportion 702 may exist in the initial or beginning portion of theUL-centric subframe. The control portion 702 in FIG. 7 may be similar tothe control portion described above with reference to FIG. 6. TheUL-centric subframe may also include an UL data portion 704. The UL dataportion 704 may sometimes be referred to as the payload of theUL-centric subframe. The UL data portion may refer to the communicationresources utilized to communicate UL data from the subordinate entity(e.g., UE) to the scheduling entity (e.g., UE or BS). In someconfigurations, the control portion 702 may be a physical DL controlchannel (PDCCH).

As illustrated in FIG. 7, the end of the control portion 702 may beseparated in time from the beginning of the UL data portion 704. Thistime separation may sometimes be referred to as a gap, guard period,guard interval, and/or various other suitable terms. This separationprovides time for the switch-over from DL communication (e.g., receptionoperation by the scheduling entity) to UL communication (e.g.,transmission by the scheduling entity). The UL-centric subframe may alsoinclude a common UL portion 706. The common UL portion 706 in FIG. 7 maybe similar to the common UL portion 706 described above with referenceto FIG. 7. The common UL portion 706 may additionally or alternativelyinclude information pertaining to channel quality indicator (CQI),sounding reference signals (SRSs), and various other suitable types ofinformation. One of ordinary skill in the art will understand that theforegoing is merely one example of an UL-centric subframe andalternative structures having similar features may exist withoutnecessarily deviating from the aspects described herein.

In some circumstances, two or more subordinate entities (e.g., UEs) maycommunicate with each other using sidelink signals. Real-worldapplications of such sidelink communications may include public safety,proximity services, UE-to-network relaying, vehicle-to-vehicle (V2V)communications, Internet of Everything (IoE) communications, IoTcommunications, mission-critical mesh, and/or various other suitableapplications. Generally, a sidelink signal may refer to a signalcommunicated from one subordinate entity (e.g., UE1) to anothersubordinate entity (e.g., UE2) without relaying that communicationthrough the scheduling entity (e.g., UE or BS), even though thescheduling entity may be utilized for scheduling and/or controlpurposes. In some examples, the sidelink signals may be communicatedusing a licensed spectrum (unlike wireless local area networks, whichtypically use an unlicensed spectrum).

A UE may operate in various radio resource configurations, including aconfiguration associated with transmitting pilots using a dedicated setof resources (e.g., a radio resource control (RRC) dedicated state,etc.) or a configuration associated with transmitting pilots using acommon set of resources (e.g., an RRC common state, etc.). Whenoperating in the RRC dedicated state, the UE may select a dedicated setof resources for transmitting a pilot signal to a network. Whenoperating in the RRC common state, the UE may select a common set ofresources for transmitting a pilot signal to the network. In eithercase, a pilot signal transmitted by the UE may be received by one ormore network access devices, such as an AN, or a DU, or portionsthereof. Each receiving network access device may be configured toreceive and measure pilot signals transmitted on the common set ofresources, and also receive and measure pilot signals transmitted ondedicated sets of resources allocated to the UEs for which the networkaccess device is a member of a monitoring set of network access devicesfor the UE. One or more of the receiving network access devices, or a CUto which receiving network access device(s) transmit the measurements ofthe pilot signals, may use the measurements to identify serving cellsfor the UEs, or to initiate a change of serving cell for one or more ofthe UEs.

Example 5G System Architecture

Systems, such as 5G systems, may support Local Area Data Networks(LADN). A LADN, is a Data Network (DN) available only in certainlocations/areas (e.g., cells). A DN may provide one or more servicessuch as operator services, Internet access, 3rd party services, etc., toa UE (e.g., UE 120) connected to the DN. For example, a particularinfrastructure available at a particular location (e.g., enterprisecampus, college campus, etc.) may provide a LADN with servicesaccessible to only UEs connected to the LADN (e.g., connected to a cellof the LADN).

In certain aspects, the core network notifies the UE of the informationfor the specific LADNs which are available to the UE, and the UErequests to establish a protocol data unit (PDU) session (i.e. anassociation between the UE and a data network) with an available LADNwhile the UE is located in the area of the LADN.

FIG. 8 illustrates example non-roaming 5G system architecture, where theAUSF 810 is an Authentication Server Function (AUSF), UDM 820 is UserData Management (UDM), the AMF 830 is Access and Mobility ManagementFunction (AMF), the SMF 840 is Session Management Function (SMF), PCF850 is Point Coordination Function (PCF), AF 860 is Application Function(AF), UE 120 is User Equipment, (R)AN 870 is Radio Access Network (RAN),UPF 880 is User Plane Function (UPF), and DN 890 is data network.

FIG. 9 illustrates example non-roaming 5G system architecture for UE(s)concurrently accessing two (e.g. local and central) data networks (i.e.,data networks 892 and 894) using multiple PDU sessions. FIG. 9 shows thearchitecture for multiple PDU sessions where two SMFs 8401 and 8402 areselected for the two different PDU sessions. FIG. 10 illustrates exampleroaming 5G system architecture in cases where there is a local break outwith AF in a visited public land mobile network (VPLMN) 1040. V-PCF orvPCF 1010 refers to a visitor PCF, H-PCF or hPCF 1020 refers to a homePCF, and HPLMN 1030 refers to a home public land mobile network. FIG. 11illustrates example roaming 5G system architecture in a home routedscenario using the reference point representation. V-SMF 1110 refers toa visitor SMF, and H-SMF 1120 refers to a home

Example Connection Management for 5G User Equipments

Connection management (CM) comprises the functions of establishing andreleasing a signaling connection between a UE and the Access andMobility Management Function (AMF) over N1. This signaling connection isused to enable non-access stratum (NAS) signaling exchange between theUE and the core network. It comprises both the access network (AN)signaling connection between the UE and the AN (e.g. radio resourcecontrol (RRC) connection over 3GPP access) and the N2 connection forthis UE between the AN and the AMF.

In some embodiments, the UE may be in two CM states that reflect the NASsignaling connectivity of the UE with the AMF. The CM states are CM-IDLEand CM-CONNECTED. In a CM-IDLE case, in some embodiments, the UE mayhave no NAS signaling connection established with the AMF over N1. Insuch embodiments, the UE may perform cell selection, cell reselectionand public land mobile network (PLMN) selection. In addition, in suchembodiments, there may be no N2 and N3 connections for the UE in theCM-IDLE state.

In the CM-IDLE state, the UE may perform one or more of the followingactions. In some embodiments, the UE may respond to paging, if received,by performing a service request procedure. In some embodiments, the UEmay perform a service request procedure when the UE has uplink signalingor user data to be sent. In some embodiments, the UE may enter theCM-CONNECTED state whenever an AN signaling connection is establishedbetween the UE and the AN (e.g. entering RRC Connected state over 3GPPaccess). The transmission of an Initial NAS message (RegistrationRequest, Service Request or Deregistration Request) may initiate thetransition from the CM-IDLE state to the CM-CONNECTED state. In theCM-IDLE state, the AMF may also perform one or more of the followingactions. In some embodiments, the AMF may perform a network triggeredservice request procedure when it has signaling or mobile-terminateddata to be sent to the UE, by sending a Paging Request to the UE. Insome embodiments, the AMF may enter CM-CONNECTED whenever an N2connection is established for the UE between the AN and the AMF.

In the CM-CONNECTED state, the UE may have a NAS signaling connectionwith the AMF over N1. In the CM-CONNECTED state, in some embodiments,the UE may enter CM-IDLE state whenever the AN signaling connection isreleased (e.g. entering RRC Idle state over 3GPP access). In theCM-CONNECTED state, in some embodiments, the AMF may enter the CM-IDLEstate whenever the N2 signaling connection for the UE is released. Insome embodiments, upon the completion of a NAS signaling procedure, theAMF may decide to release the NAS signaling connection with the UE,after which the state at both the UE and the AMF may be changed toCM-IDLE. In some embodiments, the AMF may keep a UE in CM-CONNECTEDstate until the UE de-registers from the core network.

FIG. 12 further illustrates example connection management state models.In some embodiments, when a UE becomes CM-IDLE over an access, the userplane (UP) connection of the PDU sessions that were active on the accessmay go inactive. In addition to the connection management states,certain embodiments described herein relate to NAS signaling connectionmanagement. In some embodiments, NAS signaling connection management mayinclude the functions of establishing and releasing a NAS signalingconnection. In regards to NAS signaling connection establishment, insome embodiments, an NAS signaling connection establishment function maybe provided by the UE and the AMF to establish an NAS signalingconnection for a UE in CM-IDLE state. In some embodiments, when the UEin the CM-IDLE state needs to transmit an NAS message, the UE mayinitiate a Service Request or a registration procedure to establish asignaling connection to the AMF.

Also, in some embodiments, based on UE preferences, UE subscription, UEmobility pattern and network configuration, the AMF may keep the NASsignaling connection until the UE de-registers from the network. Inregards to NAS signaling connection release, in some embodiments, theprocedure of releasing an NAS signaling connection is initiated by the5G (R)AN node or the AMF. In some embodiments, the UE may assume the NASsignaling connection is released if it detects the RRC connection isreleased. After the NAS signaling connection is released, in someembodiments, the UE and the AMF may enter the CM-IDLE state.

Example System Functionality

System functionality may include registration and connection management.Registration management may be used to setup and release a signalingrelation between the UE and the network and establish the user contextin the network. More specifically, in some embodiments, a UE/user mayneed to register with the network to receive services that requireregistration. In some embodiments, to register to the selected PLMN, theUE may initiate an initial registration procedure. Also, in someembodiments, the UE may initiate a periodic registration procedure uponthe expiry of the periodic registration timer in order to maintainreachability. In addition, in some embodiments, the UE may initiate aregistration procedure upon mobility (e.g. enters new tracking area(TA)) with the network to track the UE location and for reachability.

In addition to registration management, system functionality may includeconnection management, which as described above, may be used toestablish and release the signaling connection between the UE and theAMF to provide signaling connectivity. The 5GS Connection Management(CM) states, CM-IDLE and CM-CONNECTED, describe the signalingconnectivity between the UE and the AMF.

A UE may be in a 5G CM-IDLE state when no NAS signaling connectionbetween UE and AMF exists. In CM-IDLE state, in some embodiments, the UEmay perform cell selection/reselection and PLMN selection. In addition,in some embodiments, the UE in the CM-IDLE state may respond to pagingby performing a service request procedure and perform a service requestprocedure when the UE has uplink signaling or user data to be sent.

Unlike the CM-IDLE state, the UE and the AMF may enter the CM-CONNECTEDstate when the NAS signaling connection is established between the UEand the AMF. Initial NAS messages that initiate a transition fromCM-IDLE to CM-CONNECTED state may, in some embodiments, include aRegistration Request, Service Request or De-Registration Request. Insome embodiments, the UE may be in the CM-CONNECTED state when asignaling connection between the UE and the AMF exists. In someembodiments, the UE in the CM-CONNECTED state may perform a registrationprocedure when the TA in the received system information is not in thelist of TAs that the UE registered with the network.

In some embodiments, the UE may need to register with the network to beauthorized to receive services, to enable mobility tracking, and toenable reachability. In some embodiments, the registration procedure maybe used, for example, when the UE needs to initially register to the 5Gsystem (in the mobility procedure when the UE changes to a new TA inidle mode) and when the UE performs a periodic update (due to apredefined time period of inactivity), etc.

Example Local Area Data Network Connectivity

As described above, 5G Systems may provide support for the UEs toconnect to a LADN reachable within a certain area. In order to enablethe UE to connect to the LADN, the 5G system may send a notification tothe UE including information about the LADN and its availability, etc.In some embodiments, based on the LADN information received in thenotification, the UE may then establish a PDU session to the LADN whilethe UE is located in the area. Certain embodiments described hereinrelate to details of what information (e.g. granularity of location) isprovided to the UE, when it is provided, and how it is provided.

FIG. 13 illustrates example operations 1300 for wireless communicationsby a network device, according to aspects of the present disclosure. Thenetwork device performing operations 1300 may be, for example, an accessand mobility management function (AMF). Operations 1300 begin, at 1302,by determining a set of available local area data networks (LADNs) for auser equipment (UE) based on a subscription of the UE to a set of datanetwork names (DNNs) corresponding to the set of available LADNs. At1304, operations 1300 continue by sending the UE information indicativeof the set of available LADNs and a location of availabilitycorresponding to each of the LADNs of the set of available LADNs.

FIG. 13A illustrates a communications device 1300A (i.e., AMF) that mayinclude various components (e.g., corresponding to means-plus-functioncomponents) configured to perform operations for the techniquesdisclosed herein, such as one or more of the operations illustrated inFIG. 13. The communications device 1300A includes a processing system1314 coupled to a transceiver 1312. The transceiver 1212 is configuredto transmit and receive signals for the communications device 1300A viaan antenna 1320. The processing system 1314 may be configured to performprocessing functions for the communications device 1300A, such asprocessing signals, etc.

The processing system 1314 includes a processor 1309 coupled to acomputer-readable medium/memory 1310 via a bus 1324. In certain aspects,the computer-readable medium/memory 1310 is configured to storeinstructions that when executed by processor 1309, cause the processor1309 to perform one or more of the operations illustrated in FIG. 13, orother operations for performing the various techniques discussed herein.

In certain aspects, the processing system 1314 further includes adetermining component 1320 for performing one or more of the operationsillustrated at 1302 in FIG. 13. Additionally, the processing system 1314includes a sending component 1322 for performing one or more of theoperations illustrated at 1304 in FIG. 13.

The determining component 1320 and the sending component 1322 may becoupled to the processor 1309 via bus 1324. In certain aspects, thedetermining component 1320 and the sending component 1322 may behardware circuits. In certain aspects, the determining component 1320and the sending component 1322 may be software components that areexecuted and run on processor 1309.

FIG. 14 illustrates example operations 1400 for wireless communicationsby a wireless device, according to aspects of the present disclosure.The wireless device performing operations 1400 may be, for example, aUE. Operations 1400 begin, at 1402, by requesting information relatingto one or more local area data networks (LADNs) from an access andmobility management function (AMF). At 1404, operations 1400 continue byreceiving information from the AMF corresponding to a set of availableLADNs and an area of availability corresponding to each of the LADNs ofthe set of available LADNs, wherein the UE has a subscription to a setof data network names (DNNs) corresponding to the set of availableLADNs. At 1406, operations 1400 continue by establishing a protocol dataunit (PDU) session to one LADN of the set of available LADNs based onthe information received from the AMF.

FIG. 14A illustrates a communications device 1400A (i.e., UE 120) thatmay include various components (e.g., corresponding tomeans-plus-function components) configured to perform operations for thetechniques disclosed herein, such as one or more of the operationsillustrated in FIG. 14. The communications device 1400A includes aprocessing system 1414 coupled to a transceiver 1412. The transceiver1412 is configured to transmit and receive signals for thecommunications device 1400A via an antenna 1420. The processing system1414 may be configured to perform processing functions for thecommunications device 1400A, such as processing signals, etc.

The processing system 1414 includes a processor 1409 coupled to acomputer-readable medium/memory 1410 via a bus 1424. In certain aspects,the computer-readable medium/memory 1410 is configured to storeinstructions that when executed by processor 1409, cause the processor1409 to perform one or more of the operations illustrated in FIG. 14, orother operations for performing the various techniques discussed herein.

In certain aspects, the processing system 1414 further includes arequesting component 1420 for performing one or more of the operationsillustrated at 1402 in FIG. 14. Additionally, the processing system 1414includes a receiving component 1422 for performing one or more of theoperations illustrated at 1404 in FIG. 14. Further, the processingsystem 1414 includes an establishing component 1426 for performing oneor more of the operations illustrated at 1406 in FIG. 14.

The requesting component 1420, the receiving component 1422, and theestablishing component 1426 may be coupled to the processor 1409 via bus1424. In certain aspects, the requesting component 1420, the receivingcomponent 1422, and the establishing component 1426 may be hardwarecircuits. In certain aspects, the requesting component 1420, thereceiving component 1422, and the establishing component 1426 may besoftware components that are executed and run on processor 1409.

As described above, the embodiments described herein relate to thedetails of the information (e.g. granularity of location) provided tothe UE by the 5G system in supporting the UE to connect to a LADN.

In some embodiments, LADN information that a UE requires may includedata network (DN) identification information and DN service areainformation. In some embodiments, DN identification information mayinclude the data network name (DNN) or an access point name (APN). Thisis so that the UE may be aware of which LADN the UE may be able toconnect to. In addition, the DN service area information may be providedat the Tracking Area level or Cell ID level so that the UE may be awareof where the LADN is available. For example, the DN service areainformation may indicate where the LADN is available by pointing tocertain tracking areas or cell IDs. A “Tracking Area” is the LTEcounterpart of the location/routing area and refers to a set of cells.Tracking areas can be grouped into lists of tracking areas (TA lists),which can be configured on the UE. In addition, each cell may have aCell ID that helps identify the cell. In some embodiments, some LADNsmay be available just in a single cell (e.g. a CSG cell), in a group ofcells (e.g. covering an enterprise, or a shopping mall, or an airport),an entire tracking area, or an entire registration area.

Example Providing Information to the UE

The LADN information, described above, may be provided to the UE usingone or more of multiple techniques described herein. A first techniquerelates to policy configuration in the UE. Under the first technique, insome embodiments, the home PLMN (HPLMN) may configure the information onLADN availability via policy configuration (from the Home PCF). In suchembodiments, the UE may attempt to connect to an LADN only if it islisted in the configured policy as being available in the current area.In some cases, however, this may work only for the HPLMN since the HPLMNmay not be aware of LADN availability in VPLMNs.

In some embodiments, when the UE registers to a VPLMN, the UE mayreceive a V-PCF policy for availability of LADNs in the VPLMN. In suchembodiments, the V-PCF policy may take priority over any H-PCF policythat may be configured in the UE. In such embodiments, however, aninbound roaming UE may receive a lot of information regarding LADNs thatare not applicable to the inbound roaming UE, and may not be of any useto the UE at all.

In some embodiments, especially in roaming scenarios, the specificavailability of LADNs in the current area may not be known to the PCF(e.g. in the HPLMN) or, in some embodiments, the PCF may not haveup-to-date information relating to UPF connectivity. In suchembodiments, the AMF may be kept up-to-date via operations andmanagement (OAM) and provide more precise information. Accordingly,information from the AMF (if provided) may supersede the informationincluded in the LADN policy obtained from the PCF. In some embodiments,therefore, if the UE receives information about LADNs from the AMF, itmay ignore any information for the same LADNs that the UE may havereceived from the PCF.

Under a second technique, in some embodiments, the AMF may inform a UEperforming a (re)registration of the list of available LADNs, includingthe location of the availability of each of the LADN(s). In suchembodiments, the AMF may provide information based on OAM configurationin the AMF, where such information may not be per-subscriber. In suchembodiments, the UE may attempt to connect to an LADN only if it islisted in the information available from the AMF. Such embodiments maybe implemented in non-roaming and for roaming cases, where an HPLMN LADNis available in the VPLMN. However, in some embodiments, in case of aninbound roaming UE, as in the case of the PCF-based solution, the UE mayreceive a lot of information regarding LADNs that are not applicable tothe inbound roaming UE, and may not be of any use to the UE at all. Insuch embodiments, the AMF may provide the UE with the informationdescribed above only if the UE is a roaming UE (i.e. if the UESubscriber Permanent Identity (SUPI) indicates the UE is from anotherPLMN).

Under a third technique, in some embodiments, instead of the AMFproviding information to the UE that is not per-subscriber, the AMF mayprovide the UE with information based on OAM configuration in the AMF aswell as the UE subscription (i.e., provides information only for theLADNs that are supported in the area and correspond to DNNs that the UEhas a subscription to). In such embodiments, the UE may attempt toconnect to an LADN only if it is listed in the information availablefrom the AMF. In such embodiments, providing information based on theUE's subscription may not cause a non-roaming UE or an inbound roamingUE to receive unnecessary information about LADNs. Accordingly, suchembodiments may be implemented for both non-roaming and roaming cases,where an HPLMN LADN is available in the VPLMN. Yet, in some embodiments,the AMF may provide the information described above to the UE only ifthe UE is a roaming UE (i.e. if the UE Subscriber Permanent Identity(SUPI) indicates the UE is from another PLMN).

In some embodiments, the AMF may provide the UE with LADN informationonly if the UE explicitly requests the information by providing anindication in request messages (e.g., Registration Request). In someembodiments, a UE that is not configured for any LADNs may not requestLADN information

In some embodiments, upon performing a registration management ormobility management procedure, the UE may include in the request message(e.g., Registration Request) a list of LADNs supported by the UE andconfigured in the UE. In some embodiments, the LADNs are identified by aDNN or APN. In some embodiments, the UE may include all the LADNssupported or only a subset, e.g., only when specific services orapplications are active in the UE. In some embodiments, if the AMF isconfigured with information about such LADNs, the AMF may return theLADN information. In such embodiments, in case of a roaming UE, theLADNs the UE is configured with may not be recognized by the visitedPLMN AMF. However, in some embodiments, based on roaming agreements theVPLMN may be configured with a mapping between some of the LADNs of theHPLMN and the equivalent LADNs in the VPLMN. In such embodiments, if theAMF does not support the LADN provided by the UE but has a mapping toequivalent VPLMN LADNs, the AMF may provide the UE with the DNN or APNof the equivalent VPLMN LADN and the availability information of suchLADN.

In some embodiments, when the UE receives an indication of availabilityfor a configured LADN which includes the equivalent VPLMN LADN, the UEmay then map applications and services, which were bound to theconfigured LADN, to the equivalent VPLMN LADN for the duration of the UEregistration in the PLMN. In some other embodiments, the UE may mapapplications and services to the equivalent VPLMN LADN until the UEreceives new information from the same serving PLMN for such LADNs.

Example LADN PDU Session Treatment

As discussed above, in the CM-IDLE state, the UE may perform a servicerequest procedure when the UE has uplink signaling or user data to besent. However, in some embodiments, when a PDU session to an LADN hasbeen established and the UE moves outside the area of availability ofthe LADN, the UE may not be allowed to attempt to exchange user planetraffic with the LADN. In such embodiments, when the UE leaves the areaof availability of a LADN, the 5G core network may make a change to theLADN PDU session, which comprises performing one or more actionsincluding (1) LADN PDU Session Release, (2) Indefinite LADN PDU SessionSuspension, or (3) LADN PDU Session Suspension.

FIG. 15 illustrates example operations 1500 for wireless communicationsby a network device, according to aspects of the present disclosure. Thenetwork device performing operations 1500 may be, for example, an AMF.Operations 1500 begin, at 1502, by determining that a user equipment(UE) has moved outside of an area of availability corresponding to alocal area data network (LADN) to which the UE has an establishedprotocol data unit (PDU) session. At 1504, operations 1500 continue bysending a notification request to a session management function (SMF)serving the PDU session after the determining.

FIG. 15A illustrates a communications device 1500A (i.e., AMF) that mayinclude various components (e.g., corresponding to means-plus-functioncomponents) configured to perform operations for the techniquesdisclosed herein, such as one or more of the operations illustrated inFIG. 15. The communications device 1500A includes a processing system1514 coupled to a transceiver 1512. The transceiver 1512 is configuredto transmit and receive signals for the communications device 1500A viaan antenna 1520. The processing system 1514 may be configured to performprocessing functions for the communications device 1500A, such asprocessing signals, etc.

The processing system 1514 includes a processor 1509 coupled to acomputer-readable medium/memory 1510 via a bus 1524. In certain aspects,the computer-readable medium/memory 1510 is configured to storeinstructions that when executed by processor 1509, cause the processor1509 to perform one or more of the operations illustrated in FIG. 15, orother operations for performing the various techniques discussed herein.

In certain aspects, the processing system 1514 further includes adetermining component 1520 for performing one or more of the operationsillustrated at 1502 in FIG. 15. Additionally, the processing system 1514includes a sending component 1522 for performing one or more of theoperations illustrated at 1504 in FIG. 15.

The determining component 1520 and the sending component 1522 may becoupled to the processor 1509 via bus 1524. In certain aspects, thedetermining component 1520 and the sending component 1522 may behardware circuits. In certain aspects, the determining component 1520and the sending component 1522 may be software components that areexecuted and run on processor 1509. FIG. 16 illustrates exampleoperations 1600 for wireless communications by a network device,according to aspects of the present disclosure. The network deviceperforming operations 1600 may be, for example, a session managementfunction (SMF). Operations 1600 begin, at 1602, by receiving anotification from an access and mobility management function (AMF) thata user equipment (UE) has moved outside of an area of availabilitycorresponding to a local area data network (LADN) to which the UE has anestablished protocol data unit (PDU) session. At 1604, operations 1600continue by making a change to the PDU session being served by the SMFin response to the notification.

FIG. 16A illustrates a communications device 1600A (i.e., SMF) that mayinclude various components (e.g., corresponding to means-plus-functioncomponents) configured to perform operations for the techniquesdisclosed herein, such as one or more of the operations illustrated inFIG. 16. The communications device 1600A includes a processing system1614 coupled to a transceiver 1612. The transceiver 1612 is configuredto transmit and receive signals for the communications device 1600A viaan antenna 1620. The processing system 1614 may be configured to performprocessing functions for the communications device 1600A, such asprocessing signals, etc.

The processing system 1614 includes a processor 1609 coupled to acomputer-readable medium/memory 1610 via a bus 1624. In certain aspects,the computer-readable medium/memory 1610 is configured to storeinstructions that when executed by processor 1609, cause the processor1609 to perform one or more of the operations illustrated in FIG. 16, orother operations for performing the various techniques discussed herein.

In certain aspects, the processing system 1614 further includes areceiving component 1620 for performing one or more of the operationsillustrated at 1602 in FIG. 16. Additionally, the processing system 1614includes a making a change component 1622 for performing one or more ofthe operations illustrated at 1604 in FIG. 16.

The receiving component 1620 and the making a change component 1622 maybe coupled to the processor 1609 via bus 1624. In certain aspects, thereceiving component 1620 and the making a change component 1622 may behardware circuits. In certain aspects, the receiving component 1620 andthe making a change component 1622 may be software components that areexecuted and run on processor 1609.

FIG. 17 illustrates example operations 1700 for wireless communicationsby a network device, according to aspects of the present disclosure. Thenetwork device performing operations 1700 may be, for example, an AMF.Operations 1700 begin, at 1702, by receiving a request from a sessionmanagement function (SMF) serving a protocol data unit (PDU) sessionthat a UE has established with a local area data network (LADN) toprovide the SMF with information about a location of the UE. At 1704,operations 1700 continue by providing the SMF with a notificationincluding information about the location of the UE.

FIG. 17A illustrates a communications device 1700A (i.e., AMF) that mayinclude various components (e.g., corresponding to means-plus-functioncomponents) configured to perform operations for the techniquesdisclosed herein, such as one or more of the operations illustrated inFIG. 17. The communications device 1700A includes a processing system1714 coupled to a transceiver 1712. The transceiver 1712 is configuredto transmit and receive signals for the communications device 1700A viaan antenna 1720. The processing system 1714 may be configured to performprocessing functions for the communications device 1700A, such asprocessing signals, etc.

The processing system 1714 includes a processor 1709 coupled to acomputer-readable medium/memory 1710 via a bus 1724. In certain aspects,the computer-readable medium/memory 1710 is configured to storeinstructions that when executed by processor 1709, cause the processor1709 to perform one or more of the operations illustrated in FIG. 17, orother operations for performing the various techniques discussed herein.

In certain aspects, the processing system 1714 further includes areceiving component 1720 for performing one or more of the operationsillustrated at 1702 in FIG. 17. Additionally, the processing system 1714includes a providing component 1722 for performing one or more of theoperations illustrated at 1704 in FIG. 17.

The receiving component 1720 and the providing component 1722 may becoupled to the processor 1709 via bus 1724. In certain aspects, thereceiving component 1720 and the providing component 1722 may behardware circuits. In certain aspects, the receiving component 1720 andthe providing component 1722 may be software components that areexecuted and run on processor 1709.

For LADN PDU Session Release, in some embodiments, the 5G core networkmay explicitly release the PDU session to inform the UE that theconnectivity to the LADN is no longer available. In such embodiments,the AMF may need to know the exact UE location when the UE is in theCM-CONNECTED mode and report to the SMF the location of the UE or thatthat UE had left the LADN area (i.e. “leave LADN area” event). Inaddition to LADN PDU Session Release, certain embodiments describedherein relate to (2) Indefinite LADN PDU Session Suspension, or (3) LADNPDU Session Suspension.

For Indefinite LADN PDU Session Suspension, the 5G core network maysuspend the user plane resources for the PDU session to the LADN (i.e.N3 is released), in order to allow the PDU session to remain inactiveuntil the UE re-enters the area of availability. Suspending the PDUsession may help avoid a PDU session release procedure as well as asubsequent PDU session establishment procedure as the UE leaves andenters the area of availability. In some embodiments, a suspended PDUsession may be a PDU session for which no user plane is establishedbetween the UE and the CN (i.e. no data radio bearer or connection overthe access, and no N3 connection). As discussed above, for IndefiniteLADN PDU Session Suspension, the UE may not need to re-establish the PDUsession when moving back to the LADN availability area.

For LADN PDU Session Suspension, in some embodiments, as soon as thenetwork has detected that the UE has left the area of LADN availability,the 5G core network may release the UP for the PDU session. In suchembodiments, the 5G core network may also start a UE PDU SessionSuspension Timer as well as a network (NW) PDU Session Suspension Timerat the network (e.g. the SMF) and the UE, respectively. In suchembodiments, the NW PDU Session Suspension Timer may be set for aslightly longer time period than the UE PDU Session Suspension Timer. Insuch embodiments, when the NW PDU Session Suspension Timer expires atthe network side, the network may disconnect the PDU session and,therefore, the UE may stop the UE PDU Session Suspension Timer. Also, insuch embodiments, if the UE PDU Session Suspension Timer expires at theUE side (e.g. if the UE has for some reason not received the disconnectnotification from the network), the UE may locally disconnect the PDUsession. Accordingly, for LADN PDU Session Suspension, the PDU sessionmay be maintained only for a reasonable amount of time, to address theUE's ping-pong mobility between locations while allowing the PDUdisconnection if the UE does not return to the area of availability ofthe LADN.

In some embodiments, the three PDU session treatment actions ((1) LADNPDU Session Release, (2) Indefinite LADN PDU Session Suspension, or (3)LADN PDU Session Suspension) described above may be triggered in threeways including (1) AMF-triggered PDU Treatment, (2) SMF-triggered PDUTreatment, or (3) (R)AN-triggered PDU suspension. For AMF-triggered PDUTreatment, either a LADN PDU Session Release or LADN PDU SessionSuspension may be triggered by the AMF, in some embodiments. This AMFtriggering may, in some embodiments, be based on subscriptioninformation and local policies and based on either detecting that the UEhas moved outside the service area of the LADN or receiving anindication from the (R)AN that the user plane resources for the PDUsession have been released in the AN). In such embodiments, the AMF maytrigger the SMF to drop or suspend the PDU session. Also, in suchembodiments, the AMF may send a notification request over N11 to theserving SMF to trigger the SMF to drop or suspend the PDU session. Insuch embodiments, the SW may then proceed with the indicated treatment(i.e. either drop or suspend the PDU session).

For SW-triggered PDU Treatment, either a LADN PDU Session Release or aLADN PDU Session Suspension may be triggered by the SW upon beingnotified that the UE has moved outside the area of coverage of the LADNor upon receiving an indication from the AMF, in some embodiments. Insuch embodiments, the AMF may determine that the UE has moved outsidethe service area of the LADN or receive an indication from the (R)ANthat the user plane resources for the PDU session have been released inthe AN and subsequently indicate to the SMF, serving the PDU sessioncorresponding to the LADN, that the UE is outside the area ofavailability. Accordingly, the SW may then decide whether to drop orsuspend the PDU session based on policies.

For (R)AN-triggered PDU suspension, the AN may send a trigger to the AMFthat the PDU session should be suspended. In such embodiments, eitherthe AMF-triggered or SW-triggered PDU treatments may then take place.

Example LADN Availability Awareness in the Network

In all of the three ways discussed above ((1) AMF-triggered PDUTreatment, (2) SW-triggered PDU Treatment, or (3) (R)AN-triggered PDUsuspension), the RAN may know the exact location of the UE inCM-CONNECTED (either current cell or tracking area) and may also knowthe UE location when the UE transitions from CN-IDLE to CM-CONNECTED.

For AMF-triggered PDU Treatment or SMF-triggered PDU Treatment asdescribed above, where the AN continuously reports the location to theUE to the AMF, in some embodiments, the SMF may send a PDU sessionestablishment accept message to the AMF (e.g. session management (SM)Request Acknowledgement (N2 SM information (PDU Session ID, QoS Profile,CN Tunnel Info), N1 SM Container (PDU Session Establishment Accept(Authorized QoS Rule, SSC mode)))) after a PDU session is establishedfor an LADN. In such embodiments, the SMF may include in the SM requestacknowledgement an indication for the AMF to inform the AMF that the PDUsession is for an LADN.

Upon receiving the indication from the SW that the PDU session is for aLADN, in some embodiments, the AMF may store such information and theLADN availability area together with the mapping of the PDU Session IDand the SMF ID. In some embodiments, when providing the N2 SMInformation to the AN in the N2 PDU Session Request (N2 informationreceived from SW in DL N2 Transfer Information Request, NAS message),the AMF may further include a request to the AN to report the currentserving cell of the UE.

For AMF-triggered PDU Treatment or SW-triggered PDU Treatment asdescribed above, where the AN only reports when the UE enters or exitsthe LADN availability area, in some embodiments, the SW may send a PDUsession establishment accept message to the AMF (e.g. SM RequestAcknowledgement (N2 SM information (PDU Session ID, QoS Profile, CNTunnel Info), N1 SM Container (PDU Session Establishment Accept(Authorized QoS Rule, SSC mode)))) after a PDU session is establishedfor an LADN. In such embodiments, the SW may include in the SM requestacknowledgement an indication for the AMF to inform the AMF that the PDUsession is for an LADN.

Upon receiving the indication from the SW that the PDU session is for aLADN in the SM Request Acknowledgement, in some embodiments, the AMF mayinclude in the N2 PDU Session Request (N2 information received from SWin DL N2 Transfer Information Request, NAS message) the LADNAvailability Area containing the set of cells in which the LADN isavailable and the PDU Session ID.

In addition, after receiving the N2 PDU Session Request, the LADNAvailability Area, and the PDU Session ID from the AMF, in someembodiments, the AN may send an indication LADN UE Location Change tothe AMF when the UE changes its location with respect to the LADNAvailability Area (i.e. entering or exiting). In such embodiments, theindication may contain the PDU Session ID, to inform the AMF that the UEhas entered or exited the LADN availability area.

For (R)AN-triggered PDU Suspension, in some embodiments, the SMF maysend a PDU session establishment accept message to the AMF (e.g. SMRequest Acknowledgement (N2 SM information (PDU Session ID, QoS Profile,CN Tunnel Info), N1 SM Container (PDU Session Establishment Accept(Authorized QoS Rule, session and service continuity (SSC) mode))))after a PDU session is established for an LADN. In such embodiments, theSMF may include in the SM request acknowledgement an indication for theAMF to inform the AMF that the PDU session is for an LADN. In suchembodiments, the SMF may also include in the N2SM Information a LADN ANinformation.

In such embodiments, upon receiving the indication from the SMF that thePDU session is for a LADN, the AMF may include in the N2 PDU SessionRequest (N2 information received from SMF in DL N2 Transfer InformationRequest, NAS message) the LADN Availability Area containing the set ofcells in which the LADN is available as well as the PDU Session ID.

In addition, upon receiving from the AMF the N2 PDU Session Requestcontaining the LADN Availability Area, the PDU Session ID, and the N2 SMinformation containing the LADN AN Information, in some embodiments, theAN may perform the actions described in the LADN AN information upon theUE exiting the LADN Availability Area. In some embodiments, for example,one of such actions may be to trigger a PDU Session Suspension Requestor a User Plane Suspension request message to the AMF including the PDUSession ID. In some embodiments, one of such actions may be to releasethe UE user plane resources for the PDU session (specific accessresources, e.g. radio bearers, and optionally the UL tunnel informationfor the N3 tunnel), and to trigger a PDU Session Suspension Notificationor a User Plane Suspension Notification message to the AMF including thePDU Session ID.

In some embodiments, the access network may report to the AMF the UElocation with respect to the current serving cell or tracking area whenthe UE is CM-CONNECTED or when the UE transitions from CM-IDLE toCM-CONNECTED. In some embodiments, if LADN is available only in specificcells/tracking areas of the current registration area, the AMF may needto know where exactly the UE is to take an action on the PDU session.Accordingly, the AMF may request the AN to report such information on aper-UE basis in various embodiments. In some situations, the AMF maymake such a request when the UE is subscribed to any LADN (independentlyof whether the LADN is available in a registration area that can beserved by the AMF). In some embodiments, the AMF may make such requestonly when one or more of the LADNs that the UE is subscribed to areavailable in a set of cells and/or tracking areas that can be served bythe AMF. In some embodiments, the AMF may make such request only whenone or more of the LADNs that the UE is subscribed to are available inset of cells and/or tracking areas belonging to the Registration Areathat the AMF provides to the UE upon registration management procedures.

Subsequently, the AMF may provide to the SMF information about theavailability of the LADN corresponding to a PDU session service by theSMF. After session establishment and upon determining that the PDUsession corresponds to a LADN, in some embodiments, the SMF may requestthe AMF to provide information about the availability of the LADN andprovide the DNN corresponding to the PDU session for the LADN.

In some embodiments, the SMF may request the AMF to provide the specificUE location (e.g. cell ID, tracking area, etc.). In some otherembodiments, the SMF may not be aware of the area of availability of theLADN and request the AMF to provide an indication of when the UE exitsthe area of availability of a LADN and when the UE re-enters the area ofavailability of the LADN. In some embodiments, after the PDU sessionestablishment, the AMF may store the DNN of the PDU session, as well asthe PDU Session ID and the identity of the serving SMF, in order toprovide the subscribed LADN information to the SMF.

Example Core Network Behavior Upon Suspending a PDU Session for a LADN

For LADN PDU Session Suspension as described above, whether the decisionto suspend is made by the AMF or the SMF, the SMF may notify the servingUPF(s) that the PDU session is suspended, release the N3 connectivity byinstructing the serving UPF using the N4 interface, and instruct the AN(via the AMF) to release the access network resources for the PDUsession. In case of a non-roaming UE, in some embodiments, the servingUPF that the SMF interacts with may be the home UPF (H-UPF). Incontrast, in case of a roaming UE, the serving UPF may be the visitorUPF (V-UPF).

In some embodiments, the notification from the SMF to the UPF(s) mayinclude an indication to the UPF to not buffer any downlink data whenthe PDU session is suspended and also not to provide a DL DataNotification to the SMF. In some embodiments, upon suspending a PDUsession, the SMF may start the NW PDU Session Suspension Timer. Inaddition, in some embodiments, upon suspending a PDU session, the SMFmay notify the UE that the PDU session is suspended using two differenttechniques. Under a first technique, the SMF may send an explicit NASPDU Suspension Notification message to the UE containing the PDU SessionID. In such embodiments, the UE may respond to the NAS PDU SuspensionNotification message with a NAS PDU Suspension Accept.

Under a second technique, the SMF may indicate in its request to theAMF, for triggering the access network resource release, that therelease is related to a PDU session suspension. In some embodiments, theAMF may provide the information obtained from the SMF to the accessnetwork, and the access network (e.g. the RAN) may send to the UE anaccess network resources release request (e.g. an RRC reconfigurationmessage that releases the bearers of the PDU session) containing anindication that the request relates to a PDU session suspension.

In some embodiments, the UE may start the UE PDU Session SuspensionTimer for a PDU session when (1) the UE leaves the area of availabilityof the LADN corresponding to the PDU session, (2) the UE receives a NASPDU Suspension Notification message, or (3) the UE receives from thenetwork (e.g. the RAN) an access network resources release request (e.g.an RRC reconfiguration message that releases the bearers of the PDUsession) containing an indication that the request relates to a PDUsession suspension. Where the UE receives from the network an accessnetwork resources release request containing an indication that therequest relates to a PDU session suspension, in some embodiments, the UEmay identify the PDU session being suspended based on the mappingbetween the access network resources being suspended and the PDUsession.

Example Treatment of DL Data for a Suspended PDU Session for a LADN

In some embodiments, if the network “suspends” a PDU session to a LADNbecause the UE is outside the area of availability for the LADN, or theUE is CM-IDLE, the network behavior for DL data for a PDU sessioncorresponding to a LADN may differ from the network behavior in thegeneral case of DL data for a “suspended” PDU session.

In some embodiments, under the AMF-controlled PDU Treatment, when the UEis outside the area of availability of a LADN and the serving AMFreceives a request via N11 to establish connectivity with the UE (e.g.send a Paging Request to a CM-IDLE UE, or send a Network TriggeredService request to a CM-CONNECTED UE) from an SMF serving a suspendedPDU session corresponding to a LADN (i.e. a PDU session for which nouser plane connectivity exists between the UE and the CN, i.e. no dataradio bearers and no N3 connectivity), the AMF may reject the requestfrom the SMF if the UE is outside the area of availability of the LADN.In some embodiments, the AMF may not send a Paging Request to a CM-IDLEUE, or send a Network Triggered Service request to a CM-CONNECTED UE,upon receiving a request corresponding to a PDU session for a LADN ifthe UE is outside the area of coverage of the LADN. In some embodiments,the AMF may additionally inform the SMF that no further requests toestablish connectivity with the UE may be sent by the SMF via N11.

In some embodiments, for the SMF-controlled PDU Treatment, if a PDUsession is suspended, upon receiving a DL Data notification from aserving UPF, the SMF may discard the notification and also may nottrigger a request towards the AMF to establish connectivity with the UE.In some embodiments, the SMF may also indicate to the UPF(s) to stopbuffering data and also may not provide further DL Data Notificationmessages.

In some embodiments, for AMF-controlled PDU Treatment, the AMF mayinform the SMF that the LADN is available, when the UE enters the areaof availability of a LADN, if the UE has a suspended PDU sessioncorresponding to the LADN.

In some embodiments, when the SMF receives a notification from the AMFthat the UE is in the area of availability of a LADN for which the UEhas a suspended PDU session, the SMF may send a request to the servingUPF(s) to resume buffering data and send DL data notifications to theUE.

In some embodiments, when a suspended PDU session is resumed by the UE,the SMF may set up (i.e., activate) the user plane connection over theaccess and over N3 and also instruct the serving UPF(s) to resumebuffering data and send DL data notifications to the UE.

Example UE Explicitly Resuming a Suspended PDU Session for a LADN

In some embodiments, when outside the area of availability of a LADN,the UE may not attempt to establish a PDU session to the LADN. In someembodiments, if the PDU session is already established but no user planeresources are active for the PDU session, the UE may not send a ServiceRequest to establish resources for the PDU session for the LADN.

Accordingly, in some embodiments, in order to support LADNs, a UE inCM-IDLE state may perform a service request procedure when the UE hasuplink user data to be sent corresponding to a PDU session for a LADNand the UE is in the area of availability of the LADN. As a result, whenthe UE is CM-IDLE, upon determining that the UE has uplink data for aPDU session that corresponds to a LADN, in some embodiments, the UE mayverify whether the UE is in the area of availability of the LADN. Insome embodiments, a UE in CM-IDLE state may not perform a servicerequest procedure when the UE has uplink user data to be sentcorresponding to a PDU session for a LADN and the UE is outside the areaof availability of the LADN.

Example UE Implicitly Resuming a Suspended PDU Session for a LADN

In some embodiments, for a PDU session corresponding to a LADN, the UEmay provide an indication to the network of whether a suspended PDUsession corresponding to the LADN may automatically be re-establishedupon the UE entering the area of availability of the LADN. In someembodiments, under an AMF-controlled PDU Treatment, the UE may providethe indication to the AMF either at PDU session establishment, or in anRM procedure by providing the DNN corresponding to the LADN and theindication of implicit resuming. When the PDU session is suspended, uponthe UE entering the area of availability of the LADN, the AMF triggers anotification over N11 to re-establish the user plane resources for thePDU session by triggering a NW triggered Service Request. In someembodiments, under an SMF-controlled PDU Treatment, the UE may providethe indication to the SMF at PDU session establishment. Upon receivingan indication from the AMF that the UE has entered the area ofavailability of the LADN, in some embodiments, the SMF may trigger anetwork triggered service request for the PDU session.

The methods disclosed herein comprise one or more steps or actions forachieving the described method. The method steps and/or actions may beinterchanged with one another without departing from the scope of theclaims. In other words, unless a specific order of steps or actions isspecified, the order and/or use of specific steps and/or actions may bemodified without departing from the scope of the claims.

As used herein, a phrase referring to “at least one of” a list of itemsrefers to any combination of those items, including single members. Asan example, “at least one of: a, b, or c” is intended to cover a, b, c,a-b, a-c, b-c, and a-b-c, as well as any combination with multiples ofthe same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b,b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c).

As used herein, the term “determining” encompasses a wide variety ofactions. For example, “determining” may include calculating, computing,processing, deriving, investigating, looking up (e.g., looking up in atable, a database or another data structure), ascertaining and the like.Also, “determining” may include receiving (e.g., receiving information),accessing (e.g., accessing data in a memory) and the like. Also,“determining” may include resolving, selecting, choosing, establishingand the like.

The previous description is provided to enable any person skilled in theart to practice the various aspects described herein. Variousmodifications to these aspects will be readily apparent to those skilledin the art, and the generic principles defined herein may be applied toother aspects. Thus, the claims are not intended to be limited to theaspects shown herein, but is to be accorded the full scope consistentwith the language claims, wherein reference to an element in thesingular is not intended to mean “one and only one” unless specificallyso stated, but rather “one or more.” Unless specifically statedotherwise, the term “some” refers to one or more. All structural andfunctional equivalents to the elements of the various aspects describedthroughout this disclosure that are known or later come to be known tothose of ordinary skill in the art are expressly incorporated herein byreference and are intended to be encompassed by the claims. Moreover,nothing disclosed herein is intended to be dedicated to the publicregardless of whether such disclosure is explicitly recited in theclaims. No claim element is to be construed under the provisions of 35U.S.C. § 112, sixth paragraph, unless the element is expressly recitedusing the phrase “means for” or, in the case of a method claim, theelement is recited using the phrase “step for.”

The various operations of methods described above may be performed byany suitable means capable of performing the corresponding functions.The means may include various hardware and/or software component(s)and/or module(s), including, but not limited to a circuit, anapplication specific integrated circuit (ASIC), or processor. Generally,where there are operations illustrated in figures, those operations mayhave corresponding counterpart means-plus-function components withsimilar numbering.

For example, means for transmitting and/or means for receiving maycomprise one or more of a transmit processor 420, a TX MIMO processor430, a receive processor 438, or antenna(s) 434 of the base station 110and/or the transmit processor 464, a TX MIMO processor 466, a receiveprocessor 458, or antenna(s) 452 of the user equipment 120.Additionally, means for generating, means for multiplexing, and/or meansfor applying may comprise one or more processors, such as thecontroller/processor 440 of the base station 110 and/or thecontroller/processor 480 of the user equipment 120.

The various illustrative logical blocks, modules and circuits describedin connection with the present disclosure may be implemented orperformed with a general purpose processor, a digital signal processor(DSP), an application specific integrated circuit (ASIC), a fieldprogrammable gate array (FPGA) or other programmable logic device (PLD),discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described herein.A general-purpose processor may be a microprocessor, but in thealternative, the processor may be any commercially available processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

If implemented in hardware, an example hardware configuration maycomprise a processing system in a wireless node. The processing systemmay be implemented with a bus architecture. The bus may include anynumber of interconnecting buses and bridges depending on the specificapplication of the processing system and the overall design constraints.The bus may link together various circuits including a processor,machine-readable media, and a bus interface. The bus interface may beused to connect a network adapter, among other things, to the processingsystem via the bus. The network adapter may be used to implement thesignal processing functions of the PHY layer. In the case of a userterminal 120 (see FIG. 1), a user interface (e.g., keypad, display,mouse, joystick, etc.) may also be connected to the bus. The bus mayalso link various other circuits such as timing sources, peripherals,voltage regulators, power management circuits, and the like, which arewell known in the art, and therefore, will not be described any further.The processor may be implemented with one or more general-purpose and/orspecial-purpose processors. Examples include microprocessors,microcontrollers, DSP processors, and other circuitry that can executesoftware. Those skilled in the art will recognize how best to implementthe described functionality for the processing system depending on theparticular application and the overall design constraints imposed on theoverall system.

If implemented in software, the functions may be stored or transmittedover as one or more instructions or code on a computer readable medium.Software shall be construed broadly to mean instructions, data, or anycombination thereof, whether referred to as software, firmware,middleware, microcode, hardware description language, or otherwise.Computer-readable media include both computer storage media andcommunication media including any medium that facilitates transfer of acomputer program from one place to another. The processor may beresponsible for managing the bus and general processing, including theexecution of software modules stored on the machine-readable storagemedia. A computer-readable storage medium may be coupled to a processorsuch that the processor can read information from, and write informationto, the storage medium. In the alternative, the storage medium may beintegral to the processor. By way of example, the machine-readable mediamay include a transmission line, a carrier wave modulated by data,and/or a computer readable storage medium with instructions storedthereon separate from the wireless node, all of which may be accessed bythe processor through the bus interface. Alternatively, or in addition,the machine-readable media, or any portion thereof, may be integratedinto the processor, such as the case may be with cache and/or generalregister files. Examples of machine-readable storage media may include,by way of example, RAM (Random Access Memory), flash memory, ROM (ReadOnly Memory), PROM (Programmable Read-Only Memory), EPROM (ErasableProgrammable Read-Only Memory), EEPROM (Electrically ErasableProgrammable Read-Only Memory), registers, magnetic disks, opticaldisks, hard drives, or any other suitable storage medium, or anycombination thereof. The machine-readable media may be embodied in acomputer-program product.

A software module may comprise a single instruction, or manyinstructions, and may be distributed over several different codesegments, among different programs, and across multiple storage media.The computer-readable media may comprise a number of software modules.The software modules include instructions that, when executed by anapparatus such as a processor, cause the processing system to performvarious functions. The software modules may include a transmissionmodule and a receiving module. Each software module may reside in asingle storage device or be distributed across multiple storage devices.By way of example, a software module may be loaded into RAM from a harddrive when a triggering event occurs. During execution of the softwaremodule, the processor may load some of the instructions into cache toincrease access speed. One or more cache lines may then be loaded into ageneral register file for execution by the processor. When referring tothe functionality of a software module below, it will be understood thatsuch functionality is implemented by the processor when executinginstructions from that software module.

Also, any connection is properly termed a computer-readable medium. Forexample, if the software is transmitted from a website, server, or otherremote source using a coaxial cable, fiber optic cable, twisted pair,digital subscriber line (DSL), or wireless technologies such as infrared(IR), radio, and microwave, then the coaxial cable, fiber optic cable,twisted pair, DSL, or wireless technologies such as infrared, radio, andmicrowave are included in the definition of medium. Disk and disc, asused herein, include compact disc (CD), laser disc, optical disc,digital versatile disc (DVD), floppy disk, and Blu-ray® disc where disksusually reproduce data magnetically, while discs reproduce dataoptically with lasers. Thus, in some aspects computer-readable media maycomprise non-transitory computer-readable media (e.g., tangible media).In addition, for other aspects computer-readable media may comprisetransitory computer-readable media (e.g., a signal). Combinations of theabove should also be included within the scope of computer-readablemedia.

Thus, certain aspects may comprise a computer program product forperforming the operations presented herein. For example, such a computerprogram product may comprise a computer-readable medium havinginstructions stored (and/or encoded) thereon, the instructions beingexecutable by one or more processors to perform the operations describedherein.

Further, it should be appreciated that modules and/or other appropriatemeans for performing the methods and techniques described herein can bedownloaded and/or otherwise obtained by a user terminal and/or basestation as applicable. For example, such a device can be coupled to aserver to facilitate the transfer of means for performing the methodsdescribed herein. Alternatively, various methods described herein can beprovided via storage means (e.g., RAM, ROM, a physical storage mediumsuch as a compact disc (CD) or floppy disk, etc.), such that a userterminal and/or base station can obtain the various methods uponcoupling or providing the storage means to the device. Moreover, anyother suitable technique for providing the methods and techniquesdescribed herein to a device can be utilized.

It is to be understood that the claims are not limited to the preciseconfiguration and components illustrated above. Various modifications,changes and variations may be made in the arrangement, operation anddetails of the methods and apparatus described above without departingfrom the scope of the claims.

What is claimed is:
 1. A method of wireless communications for an accessand mobility management function (AMF), comprising: determining that auser equipment (UE) has moved outside of an area of availabilitycorresponding to a local area data network (LADN) to which the UE has anestablished protocol data unit (PDU) session; and sending a notificationrequest to a session management function (SMF) serving the PDU sessionafter the determining.
 2. The method of claim 1, wherein thenotification request comprises a request for the SMF to suspend orrelease the PDU session.
 3. The method of claim 1, further comprising:receiving a request from the SMF to provide the SMF with an indicationof when the UE moves outside the area of availability.
 4. The method ofclaim 3, wherein the request further comprises a request from the SMF toprovide the SMF an indication of when the UE re-enters the area ofavailability.
 5. The method of claim 1, further comprising: receiving arequest from the SMF to provide the SMF with information about alocation of the UE.
 6. The method of claim 5, wherein the informationabout the location of the UE comprises at least one of a cell IDassociated with the cell in which the UE operates or a tracking area. 7.The method of claim 1, further comprising: requesting an access networkto report information about a location of the UE.
 8. The method of claim7, further comprising: receiving a notification from the access networkabout the location of the UE, wherein the determining is based on thenotification.
 9. The method of claim 1, wherein the determining is basedon receiving an indication from a radio access network (RAN) that userplane resources for the PDU session have been released in an accessnetwork (AN).
 10. The method of claim 1, wherein the PDU session isdisconnected once a timer expires.
 11. The method of claim 1, whereinthe PDU session is suspended by the SMF indefinitely in response to theSMF receiving the notification request.
 12. The method of claim 1,wherein the PDU session is released by the SMF in response to the SMFreceiving the notification request.
 13. The method of claim 1, furthercomprising: receiving, in response to the UE establishing the PDUsession to the LADN, information included in a session management (SM)Request Acknowledgement from the SMF, wherein the information informsthe AMF that the PDU session corresponds to the LADN.
 14. The method ofclaim 13, further comprising: storing the information, an area ofavailability corresponding to the LADN, and a mapping of a PDU sessionID of the PDU session to a SMF ID of the SMF.
 15. The method of claim13, further comprising: sending to a radio access network (RAN) a PDUsession request including an availability area corresponding to the LADNin response to receiving the information from the SMF.
 16. The method ofclaim 15, further comprising: receiving additional information relatingto a movement of the UE with respect to the area of availability of theLADN.
 17. A method of wireless communications for a session managementfunction (SMF), comprising: receiving a notification from an access andmobility management function (AMF) that a user equipment (UE) has movedoutside of an area of availability corresponding to a local area datanetwork (LADN) to which the UE has an established protocol data unit(PDU) session; and making a change to the PDU session being served bythe SMF in response to the notification.
 18. The method of claim 17,wherein making the change to the PDU session comprises releasing the PDUsession.
 19. The method of claim 17, wherein making the change to thePDU session comprises suspending the PDU session.
 20. The method ofclaim 19, wherein the PDU session is disconnected once a timer expires.21. The method of claim 19, wherein the PDU session is suspended by theSMF indefinitely.
 22. The method of claim 17, further comprising:sending, in response to the UE establishing the PDU session to the LADN,information included in a session management (SM) RequestAcknowledgement to the AMF, wherein the information informs the AMF thatthe PDU session corresponds to the LADN.
 23. The method of claim 17,further comprising: requesting from the AMF information relating to anavailability of the LADN.
 24. The method of claim 17, furthercomprising: starting a timer for disconnecting the PDU session when theUE moves outside the area of availability corresponding to the LADN. 25.The method of claim 17, further comprising: receiving anothernotification from the AMF that the UE has re-entered the area ofavailability corresponding to the LADN; triggering a network triggeredservice request for the PDU session; and activating a user planeconnection with a core network.
 26. A method of wireless communicationsfor an access and mobility management function (AMF), comprising:receiving a request from a session management function (SMF) serving aprotocol data unit (PDU) session that a UE has established with a localarea data network (LADN) to provide the SMF with information about alocation of the UE; and providing the SMF with a notification includinginformation about the location of the UE.
 27. The method of claim 26,wherein the information about the location of the UE comprises at leastone of a cell ID associated with the cell in which the UE operates or atracking area.
 28. The method of claim 26, wherein the notificationindicates to the SMF that the UE has moved outside of an area ofavailability of the LADN.
 29. The method of claim 28, wherein thenotification indicates to the SMF that the UE has reentered the area ofavailability of the LADN.